METHOD FOR A MOBILE STATION ABLE TO SEND CONFIRMATION INFORMATION BASED ON EVENT, TANGIBLE STORAGE D

专利摘要:
methods and devices to prevent duplicate queries and event-based confirmations from being transmitted to the mobile station. methods and devices to prevent transmission from the mobile station of queries and duplicate event-based confirmations are revealed. an exemplary method for a mobile station configured to avoid event-based confirmation information as disclosed here comprises classifying a downlink data block as unreported, receiving a query from a network requesting that the mobile station send the confirmation information queried during a period and restrain sending during the period of event-based confirmation information for the downlink data block classified as unreported.
公开号:BR112012008171B1
申请号:R112012008171-3
申请日:2010-08-31
公开日:2021-03-30
发明作者:Satish Venkob；Dennis Conway；David Philip Hole
申请人:Blackberry Limited；
IPC主号:

专利说明:

CROSS REFERENCE WITH RELATED ORDER
This application claims the benefit of and priority for United States Patent Application No. 12 / 551,161, filed on August 31, 2009 under the title METHODS AND APPARATUS TO AVOID MOBILE STATION TRANSMISSION OF DUPLICATE EVENT-BASED AND POLLED ACKNOWLEDGMENTS.
The contents of the above patent application are expressly incorporated herein by reference in the detailed description contained herein.
FIELD OF REVELATION
This disclosure refers, in general, to the transmission processing of the mobile station and, more particularly, to methods and apparatus to prevent transmission by the mobile station of duplicate queries and event-based confirmations.
PRECEDENTS
Many communication systems use automatic repetition request (ARQ) techniques that allow a transmitter to confirm that data transmissions have been successfully received by a planned receiver. A typical ARQ technique involves the receiver responding to the transmitter with the confirmation information for each data block received, with the confirmation information identifying the data block being confirmed. Confirmation information may include a positive acknowledgment (referred to here as an “ACK”) indicating that the data block has been successfully received, a
negative confirmation (referred to here as "NACK") indicating I
that the receipt of the data block was unsuccessful, as well as any other appropriate confirmation information. For example, in an improved general packet radio service communication system (EGPRS), a receiver can acknowledge receipt of the radio link control (RLC) data blocks using RLC / MAC control messages (where MAC refers to the medium access control), such as an ACPR / NACK control message of the packet downlink 10 (PDAN) of the EGPRS or an ACK / NACK control message of the packet uplink.
In the case of a two-way communications system, such as an EGPRS system, the latency associated with the use of separate control messages to send the confirmation information can be reduced (without significantly decreasing the available bandwidth for transmitting the data ) including such confirmation information with blocks of data to be transmitted in the opposite direction. For example, EGPRS supports such a 20 latency reduction through its fast ACK / NACK (FANR) reporting procedure. The FANR procedure allows the confirmation information to be superimposed with an RLC / MAC data block subsequently sent from a receiving unit to a transmitting unit using the superimposed ACK / NACK (PAN) field. EGPRS mobile stations can support two types of FANR procedures, namely, FANR consulted and FANR based on the event. In addition, EGPRS mobile stations are able to respond to queries by requesting that confirmation information be sent using PDAN control messages.
instead of PAN fields. In some scenarios, a station i
conventional EGPRS mobile phone will send the duplicate confirmation information generated by these different confirmation procedures.
5 BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 is a block diagram of an exemplary EGPRS communication system capable of supporting the methods and devices described here.
Figure 2 is a block diagram of a station
10 exemplary mobile executing the avoidance of duplicate confirmation according to the methods and devices described here that can be used in the exemplary EGPRS communication system of figure 1.
Figure 3 represents a sequence diagram of
15 exemplary message illustrating the conventional acknowledgment processing performed by the exemplary EGPRS communication system in figure 1.
Figure 4 represents a diagram of the exemplary message sequence illustrating a first procedure for avoiding exemplary duplicate confirmation performed by the exemplary EGPRS communication system of figure 1.
Figure 5 represents a diagram of the exemplary message sequence illustrating a second exemplary duplicate confirmation avoidance procedure performed by the
25 exemplary EGPRS communication system in figure 1.
Figures 6A-B collectively illustrate a flowchart representative of an exemplary process that can be performed to implement avoidance of duplicate confirmation in the exemplary mobile station of figure 2.
30 Figure 7 is a flow chart representative of a
exemplary process for evaluating non-acknowledgment criteria that can be used to implement the exemplary process of figures 6A-B or the exemplary mobile station of figure 2 or both.
5 Figure 8 is a block diagram of a
exemplary processing that can store and execute exemplary machine-readable instructions used to implement some or all of the processes in figures 6A-B or 7, or both, to implement the exemplary mobile station 10 in figure 2, the exemplary EGPRS communication system from figure 1 or both.
DETAILED DESCRIPTION
Methods and devices to prevent transmission by the mobile station of queries based on duplicate event-based confirmations are revealed here. A first exemplary duplicate confirmation avoidance technique revealed here involves an exemplary mobile station being configured to send confirmation information based on the event (for example, the confirmation information generated proactively to report missing downlink data blocks not reported). The technique then involves the mobile station classifying a downlink (DL) data block as unreported (for example, when the mobile station initially determines that the DL data block is absent). The technique also involves the mobile station receiving a query from a network asking the mobile station to send the queried confirmation information (for example, confirmation information sent in response to the network query) for a period (for example, such as 0 a radio block period). Furthermore, this
The technique involves the mobile station curbing the sending, during the period, of the event-based confirmation information to the DL data block classified as unreported.
In a second exemplary duplicate acknowledgment avoidance technique disclosed here, an exemplary mobile station includes an event-based acknowledgment processor to generate event-based acknowledgment for a DL data block classified as unreported. The mobile station implementing this technique also includes a polled acknowledgment processor to generate the polled polling information in response to a poll received from a network. In addition, the mobile station implementing this technique includes a confirmation transmission unit to curb the sending of event-based confirmation information during the period when the consulted confirmation information is also to be sent during the period.
As described in more detail below, in a particular exemplary implementation of any of the 20 preceding techniques, the mobile station and the network can support EGPRS FANR, which includes a consulted FANR procedure and an event-based FANR procedure. In such an exemplary EGPRS implementation, the network can query the mobile station to respond with confirmation information for DL data blocks previously sent over the network to the mobile station. The confirmation information from the DL can take the form of a reported bitmap (RB) field including a set of confirmation bits, with each bit providing an ACK or NACK 30 indication for a respective received data block being confirmed.
by RB.
In an EGPRS implementation according to the third generation partnership project (3GPP) version 7, the network can implement the query by setting bits in a combined EGPRS query / complementary field (CES / P) included with a data block from the DL sent to the mobile station. The bits in the CES / P field are set to indicate whether the DL confirmation information is to be provided through a PAN field generated using the FANR 10 procedure consulted and sent with a data link of the uplink (UL) destined for the network or via a PDAN control message. The CES / P field can also be used to indicate during which period of the radio block the mobile station must respond with the confirmation information consulted.
Additionally or alternatively, the mobile station in such an exemplary EGPRS implementation can be commanded by the network to use the event-based FANR procedure to proactively send confirmation information from the DL at 20 regardless of whether a query is received from the network. In fact, if the event-based FANR procedure is enabled, it is generally expected that the mobile station will report any missing DL data blocks at the earliest opportunity using a PAN field sent with a UL data block destined for the network. For example, the mobile station is able to determine whether DL data blocks transmitted over the network are missing (for example, not received, received out of order, received with errors, etc.) by decoding a sequence number from block 30 (BSN) transmitted with each data block. The mobile station
classifies missing data blocks as NOT REPORTED or REPORTED. A missing data block is classified as NOT REPORTED when the missing data block was initially detected and its acknowledgment status has not yet been reported to the network. The missing data block is then classified as REPORTED when its acknowledgment status is reported to the network in any way (for example, via a consulted PAN, an event-based PAN, a control message, etc.). If the event-based FANR is enabled, it is generally required that the mobile station report the DL confirmation information (for example, as in the form of an RB field) via PAN fields generated by the event-based FANR procedure and sent with associated UL data blocks destined for the network while any missing DL data blocks are classified as UNREPORTED. Furthermore, if the event-based FANR is enabled, the mobile station needs to send an event-based PAN reporting a particular missing data block from the unreported DL during the second period of the radio block following the period of the block in which the data block of the particular DL was initially detected as missing.
5
10
15
20
25
30
As described in more detail below, mobile stations supporting the EGPRS FANR feature together with the exemplary duplicate confirmation avoidance techniques described here exhibit substantial benefits over conventional mobile stations. For example, a conventional EGPRS mobile station as per 3GPP version 7 with event-based FANR enabled typically sends an event-based PAN when any missing DL data blocks are
classified as NOT REPORTED regardless of whether the acknowledgment status of these missing DL data blocks will also be reported during the same radio block period by a consulted PAN or a PDAN control message sent in response to a network query. Such a conventional operation can result in redundant acknowledgment information being sent to the network during the same radio block period, thereby expending precious bits / bandwidth that could otherwise be used to transmit UL data.
5
10
15
20
25
30
Unlike such conventional implementations, an EGPRS mobile station supporting the exemplary duplicate confirmation avoidance techniques described here can curb the sending of an event-based PAN (or an event-based PDAN control message generated when no data is available) UL to send with event-based PAN) to report any missing DL data blocks being classified as UNREPORTED if the mobile station determines that the acknowledgment status of those missing DL data blocks will also be reported in a timely manner (or the status of confirmation has a substantial probability of also being reported in a timely manner) by a consulted PAN or PDAN control message sent in response to a network query. Using the techniques described here to curb the sending of duplicate confirmation information that would have been carried by the PAN based on the event frees up valuable bits / bandwidth that can be used to send more UL RLC / MAC data or RLC / MAC data from the Existing UL systems more robustly (for example, with a coding rate of
superior error correction, such as corresponding to a lower modulation and coding scheme (MCS) of the EGPRS). In this way, the exemplary techniques for avoiding duplicate confirmation described here are able to improve the spectral efficiency of the UL when compared to conventional confirmation processing techniques.
5
10
15
20
25
30
Referring to the figures, a block diagram of an exemplary EGPRS 100 communication system capable of supporting the duplicate confirmation avoidance techniques described here is illustrated in figure 1. The EGPRS 100 system includes an exemplary mobile station 105 in communication with an exemplary network element 110. The mobile station 105 can be implemented by any type of mobile station or end user equipment, such as a mobile phone device, a fixed telephone device, a personal digital assistant (PDA), etc. The network element 110 can be implemented by any type of network communication device, such as a base station system, a radio access network, etc. As described in more detail below, mobile station 105 implements avoidance of duplicate confirmation as described here to curb the sending of duplicate DL confirmation information generated through an event-based FANR procedure when confirmation information is also to be reported timely or has a substantial probability of also being reported timely through a consulted FANR procedure or a PDAN control message sent in response to a query from the network. Although only a mobile station 105 and a network element 110 are illustrated in figure 1, the EGPRS 100 system can
support any number of mobile stations 105 and network elements 110.
5
10
15
20
25
30
The mobile station 105 of figure 1 includes an exemplary RLC / MAC transmitter 115 and an exemplary RLC / MAC receiver 120, each communicatively coupled to an antenna 125. Similarly, network element 110 of figure 1 includes an exemplary RLC / MAC transmitter 130 and an exemplary RLC / MAC receiver 135, each coupled communicatively with an antenna 140. The RLC / MAC transmitter 115 included in the mobile station 105 sends UL RLC and MAC information wirelessly through the exemplary antenna 125 for reception via the exemplary antenna. 140 by the RLC / MAC 135 receiver included in the network element 110. As illustrated in Figure 1, the UL RLC and MAC information transmitted by the RLC / MAC transmitter 115 to the RLC / MAC 135 receiver includes UL RLC / MAC control messages 145 (for example, such as EGPRS PDAN 145 control messages discussed in more detail below) transmitted through the corresponding UL physical control channels 150 or UL 155 RLC / MAC data blocks transmitted through transmission channels. corresponding UL 160 physical data. Although figure 1 represents the transmission of only one UL 155 RLC / MAC data block, depending on a particular operating scenario, one or more UL 155 RLC / MAC data blocks can be transmitted through the appropriate UL physical data channel 160. In addition, an RLC / MAC header (not shown) including, for example, the BSN (s) of one or more UL 155 RLC / MAC data blocks can also be transmitted with o one or more UL 155 RLC / MAC data blocks. In addition, an optional PAN field 185 described in more detail below
can be transmitted with one or more UL 155 RLC / MAC data blocks.
5
10
15
20
25
30
Referring again to figure 1, the RLC / MAC transmitter 130 included in the network element 110 wirelessly sends RLC and MAC information from the DL via antenna 140 for reception via antenna 125 by the exemplary RLC / MAC receiver 120 included in the station mobile 105. As illustrated in figure 1, the RLC and MAC information from the DL transmitted by the RLC / MAC 130 transmitter to the RLC / MAC 120 receiver includes RLC / MAC control messages from the DL 165 (for example, such as Packet uplink ACK / NACK 165) transmitted through corresponding DL physical control channels 170 or DL 175 RLC / MAC data blocks transmitted through corresponding DL physical data channels 180. Although figure 1 represents the transmission of only one DL 17 5 RLC / MAC data block depending on a particular operating scenario, one or more DL 17 5 RLC / MAC data blocks can be transmitted via the appropriate DL physical data channel 180. Additionally te, an RLC / MAC header (not shown) including, for example, the BSN (s) of one or more DL 175 RLC / MAC data blocks, as well as a CES / P field described in more detail below, can also be transmitted with the one or more RLC / MAC data blocks of the DL 175. In addition, an optional PAN field 190 described in more detail below can be transmitted with the one or more RLC / MAC data blocks of the DL 175.
The EGPRS 100 system implements several ARQ techniques to confirm that a transmitted RLC / MAC block of data is successfully received by its intended receiver. Of that
Thus, to confirm DL transmissions, one of the UL 14 5 RLC / MAC control messages that can be sent by the mobile station 115 RLC / MAC transmitter is an EGPRS PDAN 145 control message providing ACK indications for RLC data blocks. / MAC of the DL 175 successfully received by the RLC / MAC 120 receiver of the mobile station. In addition, the EGPRS PDAN 145 control message sent by the mobile station's RLC / MAC transmitter provides NACK indications for DL 175 RLC / MAC data blocks not successfully received by the mobile station's RLC / MAC 120 receiver.
5
10
15
20
25
30
Similarly, to confirm UL transmissions, one of the DL 165 RLC / MAC control messages that can be sent by the network element RLC / MAC transmitter 130 is a packet uplink ACK / NACK control message 165 providing indications of ACK for UL 155 RLC / MAC data blocks successfully received by the RLC / MAC 135 receiver of the network element. Additionally, the packet uplink 165 ACK / NACK control message sent by the network element RLC / MAC transmitter provides NACK indications for UL 155 RLC / MAC data blocks not successfully received by the RLC / MAC receiver 135 of the network element.
The EGPRS 100 system also implements the FANR feature to provide confirmation information with reduced latency. Without the FANR, all acknowledgments of the received RLC / MAC data blocks would need to be sent using control messages, such as EGPRS PDAN 145 control messages, ACK / NACK control messages from the 165 uplink packet, etc. Such messages from
control do not include any RLC data, although they may include other RLC / MAC control information in addition to the confirmation information. The disadvantage of using only control messages to send the confirmation information is that such an approach can be very inefficient, particularly when the confirmation information needs to be sent quickly (for example, in order to allow fast retransmissions of erroneously received blocks) or when the status of very few blocks needs to be indicated (for example, in low bandwidth transmissions). In such scenarios, the amount of confirmation information that is really useful is very small compared to the capacity of an RLC / MAC control message.
5
10
15
20
25
30
To reduce latency, the FANR feature allows confirmation information to be transmitted in a PAN field included with the transmission of an RLC / MAC data block. In the example shown in Figure 1, the confirmation information for receiving the DL 175 RLC / MAC data blocks is included in a PAN field of UL 185 (also referred to here as PAN of UL 185) transmitted with the RLC / MAC data block. Corresponding UL 155 MAC. Similarly, the confirmation information for receiving the UL 155 RLC / MAC data blocks is included in a DL 190 PAN field (also referred to here as DL 190 PAN) transmitted with the corresponding DL 175 RLC / MAC data block . As specified by the EGPRS standards, the UL 18 5 PAN includes an RB field providing a set of acknowledgment bits, with each bit providing an ACK or NACK indication for a respective received DL data block being acknowledged by the RB. The UL 185 PAN also includes a sequence number of
short start (ShortSSN) related to the BSN of the DL data block corresponding to the first data block included in the set of DL data blocks covered by the RB field. The UL 185 PAN also includes a window start field (BOW) to indicate whether the ShortSSN field indicates the identity of the DL data block corresponding to the start of the reception window maintained by the receiver providing confirmation information.
5
10
15
20
25
30
As specified by the EGPRS standards, the DL 190 PAN can use SSN-based encoding or time-based encoding. In the case of SSN based encoding, the DL 190 PAN includes an RB field, a ShortSSN field and a BOW field as described above for the UL 185 PAN. In the case of time based encoding, the DL 190 PAN includes the field RB, with the particular UL data blocks being confirmed determined based on the time the DL 190 PAN is sent.
To support FANR, the mobile station 105 of figure 1 implements both the consulted FANR procedure and the event-based FANR procedure specified in 3GPP version 7, as mentioned above. In an exemplary queried FANR operation, network element 110 queries mobile station 105 to provide DL confirmation information on the UL 185 PAN following a subsequent UL 155 RLC / MAC data block 155 (for example, to allow DL blocks transmitted unacknowledged (NACK) by the mobile station are quickly retransmitted). (When generated by the FANR procedure consulted in response to a query from the network, a UL PAN is referred to here as a consulted PAN). So, after
complete the transmission of the DL data blocks in its transmission window, the network element 110 queries the mobile station 105 to provide the DL confirmation information in a separate EGPRS PDAN control message 145 to confirm the successful reception of the data. DL data blocks. Furthermore, when mobile station 105 is queried to provide DL confirmation information on a queried PAN 185, but mobile station 105 does not have UL 15 5 RLC / MAC data blocks to send, mobile station 105 can respond for the query with a PDAN 145 control message instead of the consulted PAN 185, thus providing early confirmation of the DL data blocks and allowing the network element 110 to advance its transmission window.
5
10
15
20
25
30
As mentioned above, network element 110 can implement its queries for DL confirmation information by setting bits in the CES / P fields included with DL 175 RLC / MAC data blocks sent to mobile station 105. For example, the element network 110 can configure the CES / P fields of one or more RLC / MAC data blocks of the DL 175 to indicate that the DL confirmation information is to be provided through a consulted PAN 185 generated using the consulted and sent FANR procedure with a UL 155 data block destined for network element 110. Alternatively, network element 110 can configure the CES / P fields of one or more DL 175 RLC / MAC data blocks to indicate that the confirmation information of the DL is to be provided via a PDAN EGPRS 145 control message. The network element 110 can also use the CES / P fields to indicate during which
radio block period after transmission of the associated DL 175 RLC / MAC data blocks, the mobile station 105 is to respond with the requested consulted PAN 185 or PDAN EGPRS 145 control message.
5
10
15
20
25
30
Additionally, mobile station 105 implements the event-based FANR procedure to proactively send confirmation information from the DL regardless of whether a query is received from network element 110. In particular, mobile station 105 is able to determine whether the RLC / MAC data blocks of the DL 175 transmitted by the network element 110 are absent (for example, not received, received out of order, received with errors, etc.) by decoding the transmitted BSN with each data block 175. A mobile station 105 maintains a receive state formation, V (N), to monitor the status of the DL 175 RLC / MAC data blocks, with each element in the receive state formation V (N) associated with a data block RLC / MAC of the respective DL 175. For example, when a DL 175 RLC / MAC data block is received successfully, the mobile station 105 classifies the status of the DL 175 RLC / MAC data block as RECEIVED by adjusting the element in the formation of the receiving state V (N ) associated with the DL 175 RLC / MAC data block for a value representative of the RECEIVED state. An absent DL 175 RLC / MAC data block is classified by the mobile station 105 as having a status of NOT REPORTED or REPORTED by adjusting the element in the formation of the receiving state V (N) associated with the DL RLC / MAC data block. 175 absent for a value representative of the state NOT REPORTED or a value representative of the state REPORTED.
5
10
15
20
25
30
For example, mobile station 105 classifies a missing DL 175 RLC / MAC data block as NOT REPORTED when the missing data block is initially detected as missing and its acknowledgment status has not yet been reported for network element 110. The missing DL 175 RLC / MAC data block is then classified as REPORTED when mobile station 105 reports its acknowledgment status to network element 110 (for example, via UL 185 PAN, a PDAN 145 control message, etc.) . If event-based FANR is enabled, mobile station 105 proactively reports confirmation information from DL while any RLC / MAC data blocks of DL 175 are classified as UNREPORTED in the formation of the receiving state V (N), with DL confirmation information being reported via the UL 185 PAN generated by the event-based FANR procedure and sent with associated UL 155 RLC / MAC data blocks destined for the network element. (When proactively generated by the event-based FANR procedure, a UL PAN is referred to here as an event-based PAN). In general, mobile station 105 operates to send such a PAN based on event 185 by reporting a particular missing RLC / MAC data block of the DL 175 during the second radio block period following the block period in which the block of data from the private DL was initially detected as missing. Furthermore, when mobile station 105 generates event-based DL confirmation information to be provided in event-based PAN 185, but mobile station 105 does not have UL 155 RLC / MAC data blocks to send, the mobile station 105 can send DL confirmation information
based on the control message PDAN 145 instead of the PAN based on event 185.
5
10
15
20
25
30
Mobile station 105 also implements one or more of the duplicate confirmation avoidance techniques described here to curb the sending of duplicate DL confirmation information generated through the event-based FANR procedure and generated in response to a query from network element 110. As mentioned above, a conventional EGPRS mobile station typically sends an event-based PAN (or event-based PDAN control message instead of an event-based PAN) when any missing DL data blocks are classified as UNREPORTED despite whether the acknowledgment status of those missing DL data blocks will also be reported during the same radio block period by a consulted PAN or a PDAN control message sent in response to a query from the network. In contrast, mobile station 105 avoids sending such duplicate confirmation information, at least in some circumstances, by not sending a PAN based on event 185 (or PDAN control message based on event 145 instead of PAN based on event 185 ) if the mobile station 105 determines that the acknowledgment status of the missing DL data blocks NOT REPORTED is to be reported in due time by a consulted PAN 185 or a PDAN control message 145 sent in response to a query received from the network element 110 .
In a first example, mobile station 105 refrains from sending such a PAN based on event 185 as long as the queried PAN 18 5 or a PDAN 14 5 control message must be sent by mobile station 105 during the same period
radio block like PAN based on event 185 would have been sent. In a second example, mobile station 105 evaluates one or more non-acknowledgment criteria to determine whether to stop sending the PAN based on event 185 which duplicates the confirmation information to be sent by a consulted PAN 185 or a PDAN control message. 145 in the same radio block period. An exemplary implementation of avoiding duplicate acknowledgment at mobile station 105 is illustrated in figure 2 and discussed in more detail below.
5
10
15
20
25
30
Although the duplicate confirmation avoidance methods and devices disclosed here are described in the context of the EGPRS 100 system in Figure 1, these exemplary methods and devices can be readily adapted for use in any communication system where confirmation information can be provided both proactively through an event-based procedure and also in response to a query requesting confirmation information. Furthermore, although the exemplary methods and devices disclosed here are described from the perspective of implementation by the mobile station 105, in a communication system in which the mobile station 105 can consult the network element 110 for confirmation information, the methods and devices revealed examples could also be implemented by the network element 110 due to the symmetry of the RLC / MAC transmitters and receivers included in the mobile station 105 and in the network element 110.
A block diagram of an exemplary implementation of the mobile station 105 included in the EGPRS 100 system in figure 1 is illustrated in figure 2. In particular, figure 2
illustrates exemplary implementations of the mobile station's RLC / MAC 115 transmitter and the mobile station's RLC / MAC 120 receiver. In the example shown in Figure 2, and with reference to Figure 1, the RLC / MAC receiver 120 of the mobile station includes a query decoder 205 for decoding query messages received from a network element (for example, such as the network element 110) requesting the mobile station 105 to provide the acknowledgment status for DL data blocks (for example, such as the DL 175 RLC / MAC data block) previously transmitted over the network. For example, to implement the EGPRS queried FANR feature, query decoder 205 can decode a query message per PAN 210 received by requesting mobile station 105 to provide such confirmation information in a consulted PAN field 215 (for example, corresponding with the PAN 185 field) accompanying the UL 22 0 data blocks (for example, such as the UL 155 RLC / MAC data blocks) to be transmitted to the network. As another example, query decoder 205 can decode a received PDAN consultation message 225 by requesting that mobile station 105 provide such confirmation information in a separate PDAN EGPRS 230 control message (for example, corresponding with the PDAN control message. EGPRS 145). In an exemplary implementation, the query message by PAN 210 and the query message by PDAN 225 are implemented by the CES / P fields included with the DL data blocks, as described above.
5
10
15
20
25
30
The RLC / MAC receiver 120 of figure 2 also includes a formation of the receiving state 235 to monitor the status of a set (for example, a sequence) of blocks of
DL data (for example, such as DL 175 RLC / MAC data blocks) sent to mobile station 105 over the network. As described above, each element of the receiving state formation 235 (also referred to as V (N) here and in the figures) is associated with a data block of the respective DL in the set of DL data blocks sent to the mobile station 105 over the network. An element of the formation of the receiving state 235 can adopt a representative value of at least one of the following states: a RECEIVED state, an UNREPORTED state and a REPORTED state. A particular element of the formation of the receiving state 235 is set to RECEIVED when the data block of the DL associated with the formation element is successfully received by the mobile station 105. Conversely, the particular element of the formation of the receiving state 235 is initially set to NOT REPORTED when the associated DL data block is expected to be received from the network (for example, based on tracking the BSNs included with the DL data blocks), but is initially detected as missing and confirmation information (for example, such as a NACK) has not yet been reported to the network. That element of forming the receiving state 235 is then set to REPORTED when the acknowledgment information (e.g., such as a NACK) for the data block of the associated missing DL is subsequently reported to the network.
5
10
15
20
25
30
The RLC / MAC transmitter 115 of the mobile station of Figure 2 includes a query acknowledgment processor 240 for processing received query messages decoded by query decoder 205 and for generating appropriate queried responses. When a query message
per PDAN 225 is decoded by the query decoder 205, the processor of the consulted confirmation 240 evaluates the state information maintained by the formation of the receiving state 235 and generates the consulted confirmation information from the DL appropriate for inclusion in a PDAN 230 control message to be sent in response to the network query. For example, the consulted acknowledgment processor 240 can generate consulted acknowledgment information from the DL in the form of an ACK / NACK field that reports ACKs for all data blocks of the DL, whose associated elements of the formation of the receiving state 235 are adjusted. for RECEIVED and NACKs for all DL data blocks, whose associated elements of the formation of the receiving state 235 are set to NOT REPORTED or REPORTED. In an EGPRS implementation, the reported ACK / NACK bitmap for both queried PAN and PDAN responses starts at BSN equal to V (Q) +1, where V (Q) represents the lowest BSN not yet received and so , indicates the beginning of the window received from the mobile station. In addition, the queried confirmation processor 240 schedules the PDAN 230 control message generated for transmission during a UL radio block period indicated by the decoded PDAN inquiry message 225.
5
10
15
20
25
30
However, when a query message by PAN 210 is decoded by the query decoder 205, the query confirmation processor 240 in an exemplary implementation implements the EGPRS queried FANR procedure. In such an example, the processor of the consulted acknowledgment 240 evaluates the state information maintained by the formation of the receiving state 235 and generates a
confirmation information consulted from the DL appropriate for inclusion in a consulted PAN 215 to be sent in response to the network consultation. For example, the queried confirmation processor 240 can generate queried confirmation information from the DL in the form of an RB field for inclusion in the queried PAN 215. As described above, the RB field includes a set of confirmation bits, with each bit providing a ACK indication for a respective received DL data block and a NACK indication for a respective missing DL data block being confirmed by the RB. Along with the generation of the RB field, the processor of the consulted confirmation 240 can also generate the SSN and BOW fields appropriate for inclusion in the consulted PAN 215. Additionally, the processor of the consulted confirmation 240 schedules the consulted PAN 215 generated for transmission during a period of radio block of the UL indicated by the query message by decoded PAN 210.
5
10
15
20
25
30
The RLC / MAC 115 transmitter in figure 2 also includes a confirmation processor based on event 245 to proactively send confirmation information from the DL regardless of whether a query (for example, such as a query message by PAN 210 or a query message via PDAN 225) is received from the network. In an exemplary implementation, the event-based acknowledgment processor 245 implements the FANR procedure based on the EGPRS event. In such an example, the event-based acknowledgment processor 245 automatically processes the formation of the receiving state 235 after it is updated at the end of a radio block period.
previous DL to determine whether any DL data blocks are classified as UNREPORTED. If the event-based FANR is enabled on the mobile station 105, the event-based acknowledgment processor 245 automatically evaluates the state information maintained by the formation of the receiving state 235 and generates confirmation information based on the appropriate DL event for inclusion in a PAN based on event 25 0 (for example, corresponding to the PAN 185 field) following UL 255 data blocks (for example, such as UL 155 RLC / MAC data blocks) to be transmitted to the network. Alternatively, the 245 event-based acknowledgment processor can generate the appropriate DL event-based acknowledgment information for inclusion in a PDAN control message based on event 258 if mobile station 105 does not have UL 255 data block to send .
5
10
15
20
25
30
For example, similar to the operation of the queried confirmation processor 240, the confirmation processor based on event 245 can generate confirmation information based on the DL event in the form of an RB field for inclusion in the PAN based on event 250 (or in the message of PDAN control based on event 258), with each bit in the RB providing an ACK indication for a respective received DL data block and a NACK indication for a respective missing DL data block being confirmed by the RB. Along with the generation of the RB field, the acknowledgment processor based on event 245 can also generate the appropriate ShortSSN and BOW fields for inclusion in the PAN based on event 250 (or on the PDAN control message based on event 258). Additionally, the
confirmation based on event 245 schedules the generated PAN 250 (or the PDAN control message based on event 258) for transmission during the second period (or some other specified) of the UL radio block after initially determining that Reception 235 classified at least one block of DL data as NOT REPORTED.
5
10
15
20
25
30
The RLC / MAC transmitter 115 included in the mobile station 105 of figure 2 also includes a confirmation transmission unit 260 to implement duplicate confirmation avoidance as described here. For example, for a given uplink radio block period, acknowledgment transmission unit 260 obtains from the acknowledgment processor based on event 245 any PAN field based on event 250 (or any PDAN control message based on event 25 8 ) to be sent during the given uplink radio block period. In addition, the confirmation transmission unit 260 obtains from the queried confirmation processor 240 any queried response, such as any queried PAN 215 or PDAN control message 230, to be sent during the given uplink radio block period. If a PAN field based on event 250 (or a PDAN control message based on event 258) is scheduled to be sent during the given uplink radio block period, acknowledgment transmission unit 260 implements avoidance of duplicate acknowledgment as follows. Although the following description focusing on processing a PAN field based on event 250 is described, the following description is also applicable to processing
5
10
15
20
25
30
a PDAN control message based on event 258.
In an exemplary implementation, if a PAN field based on event 250 is scheduled to be sent during the given uplink radio block period, acknowledgment transmission unit 260 determines whether acknowledgment information based on the event of the DL to be reported through the PAN field based on event 250 (for example, reporting one or more missing DL data blocks NOT REPORTED) will remain unreported at the end of the given uplink radio block period if the PAN field based on event 250 does not is sent. To make such a determination, the acknowledgment transmission unit 260 determines whether the acknowledgment information based on the DL event (for example, RB field) to be reported via the PAN field based on event 250 is also included in any queried confirmation information. DL (for example, RB field) to be reported via a queried response, such as any queried PAN 215 or PDAN 230 control message, scheduled to be sent during the given downlink radio block period. If such a consulted response is not scheduled to be sent during the given radio block period, the acknowledgment transmission unit 260 determines that the confirmation information based on the DL event would remain unreported and thus make the PAN field based on the event 250 containing confirmation information based on the DL event being sent during the given radio block period. However, if such a consulted response is also scheduled to be sent during the given radio block period, the
confirmation 260 restrains the sending (for example, blocks) of the PAN field based on event 250 containing the confirmation information based on the DL event and causes only the consulted PAN 215 or PDAN 230 control message containing the consulted confirmation information from the DL is sent during the given radio block period. (In some instances, acknowledgment transmission unit 260 also restrains the sending of the PAN field based on event 250 if a polled response sending duplicate acknowledgment information is scheduled to be sent during a later radio block period.)
5
10
15
20
25
30
In at least some exemplary implementations, the acknowledgment transmission unit 260 still evaluates one or more acknowledgment omission criteria to determine whether to curb the sending of an event-based PAN 250 containing event-based acknowledgment information that is duplicated in the acknowledgment information. consulted confirmation to be sent by a consulted PAN 215 or a PDAN 230 control message. For example, such confirmation omission criteria may further characterize the probability of the DL's queried confirmation information by duplicating the confirmation information based on the non-DL event. be received completely by the network at the end of the given radio block period of the uplink if only the field of the consulted PAN 215 containing the confirmation information consulted from the DL is sent. In such exemplary implementations, although confirmation information based on the DL event to be sent through a PAN field based on event 250 is also scheduled to be sent by a consulted response (for example, such as a PAN
215 or a PDAN 230 control message consulted) during the given uplink radio block period, the acknowledgment transmission unit 260 causes the PAN field based on event 250 to still be sent if the confirmation omission criteria evaluated indicate a substantial probability that all confirmation information consulted from the DL (for example, containing confirmation indications reporting one or more missing DL data blocks NOT REPORTED) will not be received by the network. Conversely, the acknowledgment transmission unit 260 restrains the sending (for example, blocks) of the PAN field based on event 250 in the given UL radio block period if the evaluated acknowledgment omission criteria indicate a substantial probability that the entire DL queried confirmation information (in which the DL event based confirmation information is duplicated) scheduled to be transmitted via the queried response is substantially likely to be received by the network.
5
10
15
20
25
30
Examples of the confirmation omission criteria to be evaluated by the acknowledgment transmission unit 260 include, but are not limited to: (1) a channel quality criterion indicating whether the estimated UL's channel quality satisfies a threshold; (2) a criterion of the type of consulted response indicating whether the consulted confirmation information from the DL is to be transmitted through a consulted PAN 215 or a PDAN 230 control message; (3) a remaining confirmation quantity criterion indicating whether the amount of remaining confirmation information to be sent exceeds a threshold; (4) a downlink link assignment criterion indicating whether the
downlink channel assignment exceeds a threshold data rate or bandwidth; (5) a criterion for scheduling the consulted response indicating whether the consulted DL confirmation information including confirmation information based on the DL event is scheduled to be transmitted in the given radio block period or subsequent radio block period, etc. . The acknowledgment transmission unit 260 can be configured to evaluate any, any combination, or all the preceding acknowledgment omission criteria.
5
10
15
20
25
30
For example, the channel quality criterion indicates that the confirmation information consulted from the DL has a substantial probability of not being received by the network if the uplink channel quality does not satisfy (for example, it is less than) a threshold quality specified because the DL's queried confirmation information may become corrupted during transmission, while the DL's queried confirmation information has a substantial probability of being reported if the uplink channel quality satisfies (for example, it is greater than or equal to) the specified threshold quality. The channel quality of the uplink can be determined through any appropriate signal measurements, as well as deduced based on the modulation and coding scheme used to transmit the confirmation information.
The criterion of the type of response consulted can be used to further characterize the channel quality criterion under the scenario when the link channel quality
ascending does not satisfy (for example, is less than) the specified threshold quality. The confirmation information provided by a PAN field (for example, such as the queried PAN 215) is typically less reliable than the confirmation information provided by a packet ACK / NACK control message (for example, such as the message PDAN 230 control panel). The reduced reliability of the PAN field usually results from less error detection and correction, less robust coding, or both being used for the PAN field than for a control message. Because of a greater likelihood resulting from false positive detections, PAN fields are generally treated with caution (for example, requiring confirmation via an appropriate packet ACK / NACK control message as described above) to avoid the possibility of any failures serious problems arising in the event of such false positive detection.
5
10
15
20
25
30
Due to the reduced reliability of PAN fields in relation to control messages and because PAN fields typically cannot send as much confirmation information as control messages, the criterion of the type of the consulted response still indicates that the consulted confirmation information from the DL has a substantial probability of not being received by the network when the DL's queried confirmation information is to be reported by a queried PAN 215 and the uplink channel quality does not satisfy (for example, it is less than) the specified threshold quality. Conversely, the type of consulted response criterion indicates that the DL's consulted confirmation information has a
substantial probability of being received by the network when this information is to be reported by a PDAN 230 control message, even though the uplink channel quality does not satisfy (for example, it is less than) the specified threshold quality.
5
10
15
20
25
30
Considering the other non-confirmation criteria, the remaining confirmation quantity criterion indicates that the confirmed confirmation information from the DL duplicating the confirmation information based on the DL event has a substantial probability of not being received completely by the network at the end of the data radio block period if the amount of DL reporting information not reported exceeds a threshold. This is because all DL confirmation information (including information that would have been reported by PAN based on event 250) remaining to be reported may not be fully included in the consulted PAN 215 or PDAN 230 control message sent during the given reporting period. radio block.
The downlink channel assignment criterion indicates that the DL acknowledged confirmation information by duplicating the DL event based confirmation information has a substantial probability of not being received completely by the network at the end of the given radio block period if the downlink channel assignment exceeds a threshold data rate or bandwidth. This is because a large channel assignment can produce an amount of confirmation information that cannot be fully included in the DL confirmed query information to be reported by the consulted PAN 215 or control message.
5
10
15
20
25
30
PDAN 230 during the given radio block period.
The query response scheduling criterion indicates that confirmation information based on the DL event has a substantial probability of remaining unreported at the end of a first radio block period when that information is to be included (for example, duplicated) in the confirmation information consulted from DL to be reported in a second period of subsequent radio block. This is because confirmation information based on the DL event could be reported in the first previous radio block period if the PAN based on the corresponding 250 event was sent. This criterion for scheduling the queried response has applicability primarily to systems where the acknowledgment transmission unit 260 can also curb the sending of the PAN field based on event 250 if a queried response sending duplicate confirmation information is scheduled to be sent over a period of time. of a posterior radio block.
As mentioned above, acknowledgment transmission unit 260 can be configured to evaluate any, any combination, or all preceding acknowledgment omission criteria. For example, acknowledgment transmission unit 260 may be configured to cause a PAN field based on event 250 containing acknowledgment information based on the DL event to be sent during a given radio block period if one or more of the criteria omission of confirmation indicates that there is a substantial probability that all confirmation information consulted from the DL duplicating the confirmation information
confirmation based on the DL event will not be received completely by the network at the end of the given uplink radio block period. However, if the acknowledgment omission criteria evaluated by the acknowledgment transmission unit 260 indicates that there is a substantial probability that all the acknowledged information from the DL duplicating the confirmation information based on the DL event will be received completely by the network, the unit acknowledgment transmission 260 restrains the sending (e.g., blocks) of the PAN field based on event 250 to prevent transmission of duplicate acknowledgment information.
5
10
15
20
25
30
Additionally or alternatively, the acknowledgment transmission unit 260 can evaluate different acknowledgment criteria depending on whether confirmation information based on the DL event is to be sent via a PAN based on event 25 0 or a PDAN control based on event 258 For example, as mentioned above, receiving DL confirmation information via a PDAN control message based on event 258 allows network element 110 to advance its transmission window, while network element 110 cannot advance its transmission window if DL confirmation information is received through a PAN based on event 250 (due to the lower reliability of PAN based on event 250). In this way, the confirmation transmission unit 260 can evaluate the type of the queried response criterion and then determine that the confirmation information based on the DL event must be sent even if the duplicate information of the consulted DL confirmation is sent.
to be sent if confirmation information based on the DL event is to be sent via the PDAN control message based on event 258 and the confirmed confirmation information from the DL is to be reported through a consulted PAN 215.
5
10
15
20
25
30
Although an exemplary way of implementing the exemplary mobile station 105 of figure 1 has been illustrated in figure 2, one or more of the elements, processes and / or devices illustrated in figure 2 can be combined, divided, rearranged, omitted, eliminated and / or implemented in any other way. In addition, the exemplary RLC / MAC transmitter 115, the exemplary RLC / MAC receiver 120, the exemplary query decoder 205, the formation of the exemplary receive state 235, the queried confirmation processor 240 exemplary, the event based confirmation processor Exemplary 245, the confirmatory transmission unit 260 exemplary and / or more generally, the exemplary mobile station 105 of figure 2 can be implemented by hardware, software, firmware and / or any combination of hardware, software and / or firmware. Thus, for example, any of the exemplary RLC / MAC transmitter 115, the exemplary RLC / MAC receiver 120, the exemplary query decoder 205, the formation of the exemplary receive state 235, the processor of the queried confirmation 240 exemplary, the confirmation based on the exemplary event 245, the 260 exemplary confirmation transmission unit and / or more generally, the exemplary mobile station 105 could be implemented by one or more circuits, programmable processor (s), integrated circuit (s) ( s) application
specific (ASIC (s)), programmable logic device (s) (PLD (s)) and / or field programmable logic device (s) (FPLD (s)), etc. When any of the attached claims is read to cover a purely software and / or firmware implementation, at least one of the exemplary mobile station 105, the exemplary RLC / MAC 115 transmitter, the exemplary RLC / MAC 120 receiver, the query decoder 205 example, the formation of the exemplary reception state 235, the query confirmation processor 240 example, the event based confirmation processor 245 example and / or the confirmation transmission unit 260 example is here expressly defined including a tangible medium, such as a memory, digital versatile disc (DVD), compact disc (CD), etc., storing such software and / or firmware. Still further, the exemplary mobile station 105 of figure 2 may include one or more elements, processes and / or devices in addition to, or instead of, those illustrated in figure 2 and / or may include more than one of any or all the illustrated elements, processes and devices.
5
10
15
20
25
30
Exemplary message sequence diagrams 300, 400 and 500 which still illustrate the operation of the mobile station 105 of figures 1 or 2, or both, in the EGPRS communication system 100 are shown in figures 3, 4 and 5, respectively. By reference, the message sequence diagram 300 represents the exemplary conventional acknowledgment processing that could be performed by the mobile station 105 instead of the duplicate acknowledgment avoidance techniques described here. The diagrams of
message sequences 400 and 500 then represent exemplary duplicate confirmation avoidance techniques implemented by the mobile station 105, thereby illustrating at least some of the benefits of these techniques over conventional acknowledgment processing depicted in the message sequence diagram 300.
5
10
15
20
25
30
With reference to figure 3, and with reference to figures 1 and 2, the message sequence diagram 300 begins with the mobile station 105 receiving an RLC / MAC data block from the DL 055 sent by the network element 110 during the time 0 of the N ° period of the radio block. The RLC / MAC data block of the DL 305 has a BSN set to 0 and that data block is correctly decoded by the mobile station 105. In this way, the element of formation of the receiving state 235 associated with the RLC / MAC data block DL 305 received is set to RECEIVED.
Next, mobile station 105 receives an RLC / MAC data block from DL 310 sent by network element 110 during time slot 1 of the N ° radio block period. The RLC / MAC data block of the DL 310 has a BSN set to 1, and that data block is correctly decoded by the mobile station 105. In this way, the element of formation of the receiving state 235 associated with the data block RLC / DL 310 MAC received is set to RECEIVED.
Next, mobile station 105 receives an RLC / MAC data block from DL 315 sent by network element 110 during time slot 2 of the N ° radio block period. In the illustrated example, the header of the DL 315 RLC / MAC data block is correctly decoded by the mobile station 105 and includes a CES / P field sending a confirmation query.
for mobile station 105. The confirmation query included with the DL 315 RLC / MAC data block can correspond with a query message per PAN 210 or a query message per PDAN 225. The query included with the RLC data block / MAC of the DL 315 also indicates that the response to the query (for example, such as a consulted PAN 215 or a PDAN 230 control message) is to be sent in the N + 2 radio block period (for example, two periods radio block after the query is received).
5
10
15
20
25
30
In the illustrated example, mobile station 105 also incorrectly decodes the RLC data portion of the DL 315 RLC / MAC data block (which is represented by a large "X" through the directed line marked 315), although mobile station 105 decodes the header correctly, which indicates that the BSN is set to 2. The mobile station 105 treats the DL 315 RLC / MAC data block incorrectly decoded as missing. In this way, the element of formation of the receiving state 235 associated with the missing RLC / MAC data block of the DL 315 is set to NOT REPORTED, because the acknowledgment status (for example, NACK) of that block has not yet been reported to the network element 110.
The event-based FANR procedure implemented by mobile station 105 causes an event-based PAN (for example, such as event-based PAN 250) to be proactively generated (for example, automatically) for inclusion with a data block RLC / MAC of the UL 320 to be transmitted to the network element 110 during time interval 0 of the radio block period N + 2 (that is, which is
two radio block periods after determining that the DL 315 RLC / MAC data block is incorrectly decoded with BSN = 2 is a missing block). For example, because the element of formation of the receiving state 235 associated with the missing RLC / MAC data block of the DL 315 is set to NOT REPORTED, the event-based FANR procedure implemented by the mobile station 105 automatically generates a PAN based on the event having an RB field to report, among other confirmation indications, a NACK for the RLC / MAC data block of the DL 315. In the context of the message sequence diagram 300, the mobile station 105 implements the conventional confirmation processing that does not prevent sending duplicate confirmations according to the techniques described here. Therefore, mobile station 105 automatically sends the event-based PAN generated with the UL 320 RLC / MAC data block without checking whether the confirmation information included in the event-based PAN will also be reported in response to the query included with the block. DL 315 RLC / MAC data.
5
10
15
20
25
30
Then, during time slot 1 of the N + 2 radio block period, mobile station 105 also sends a polled acknowledgment response 325 to network element 110. The polled acknowledgment response 325 can be, for example, a Consulted PAN 215 sent in response to a PAN 210 query message included with the DL 315 RLC / MAC data block, or PDAN 230 control message sent in response to a PDAN 225 consultation message included with the data block DL 315 RLC / MAC. Because the consulted confirmation reply 325 is sent in the same radio block period as the
UL 320 RLC / MAC data block including event-based PAN, network element 110 will not have had time to respond to the NACK indication provided in the event-based PAN for the missing DL 315 RLC / MAC data block . Thus, the consulted confirmation information included in the consulted confirmation response 325 will also include a NACK for the DL 315 RLC / MAC data block, duplicating the event-based confirmation information provided by the PAN based on the event included with the data block. UL 320 RLC / MAC. The message sequence diagram 300 then ends.
5
10
15
20
25
30
In an implementation according to 3GPP version 7 of EGPRS, an event-based PAN, like event-based PAN 250, has a size of 25 bits. In the exemplary message sequence diagram 300, sending duplicate event-based confirmation information in the event-based PAN included with the UL 320 RLC / MAC data block wastes transmission of bits that could be better allocated for sending more UL RLC / MAC data or more robustly existing RLC / MAC data (for example, with more coding gain).
The message sequence diagram 400 of figure 4 illustrates a first exemplary duplicate confirmation avoidance technique implemented by the mobile station 105. The operation of the message sequence diagram 400 from the reception of the RLC / MAC data block of the DL 305 to the reception of the RLC / MAC data block of the DL 315 is substantially the same as for the message sequence diagram 300 of Figure 3, which is described in detail above. In the interest of brevity, the details of the operation of the sequence diagram
message 400 from the reception of the DL 305 RLC / MAC data block to the reception of the DL 315 RLC / MAC data block are not duplicated here.
5
10
15
20
25
30
Referring to Figure 4, and as described above in conjunction with message sequence diagram 300, after receiving the RLC / MAC data block from the DL 315, the mobile station 105 illustrated in message sequence diagram 400 has classified the block DL 315 RLC / MAC data as missing (for example, setting its associated element in the formation of the receiving state 235 to NOT REPORTED). The mobile station 105 was also instructed by the network element 110 to provide the confirmation information consulted from the DL on the N + 2 radio block. However, unlike message sequence diagram 300 in Figure 3, mobile station 105 in message sequence diagram 400 does not generate an event-based PAN for inclusion with an UL 42 0 RLC / MAC data block to be sent for the network element during time slot 0 of the N + 2 radio block period, because mobile station 105 in this example implements duplicate acknowledgment avoidance.
In particular, before the start of the N + 2 radio block, mobile station 105 determines that any confirmation information based on the DL event (for example, the reporting of a NACK to the DL 315 RLC / MAC data block) that would have been reported via an event-based PAN included with the UL 420 RLC / MAC data block is also to be reported via the DL's verified confirmation information carried by the consulted confirmation response 325. Thus, mobile station 105 prevents your event-based FANR procedure from generating or at least
send an event-based PAN with the UL 4 20 RLC / MAC data block. In an implementation of 3GPP EGPRS version 7, such avoidance of duplicate confirmation saves 25 bits in the UL 42 0 RLC / MAC data block that can be allocated to send more RLC / MAC data from the UL or existing RLC / MAC data more robustly (for example, with more coding gain).
5
10
15
20
25
30
The message sequence diagram 500 of figure 5 illustrates a second exemplary duplicate confirmation avoidance technique implemented by the mobile station 105. With reference to figures 1 and 2, the message sequence diagram 500 begins with the mobile station 105 receiving a query acknowledgment 505 of network element 110 requesting the acknowledgment status of the DL. Confirmation query 505 is received by mobile station 105 during or before the N ° radio block period, and indicates that mobile station 105 must respond to the query in the N + 2 radio block period or some block period posterior radio. Confirmation query 505 can correspond with a query message by PAN 210 or a query message by PDAN 225 implemented, for example, by one or more CES / P fields included with the DL RLC / MAC data blocks sent by the element network 110 to mobile station 105.
During or before the N ° radio block period, mobile station 105 also detects an absent DL RLC / MAC data block (represented by the directed line marked 510 in figure 5). In this way, the element of formation of the receiving state 235 associated with the missing data block 510 is set to NOT REPORTED, because the state
acknowledgment (for example, NACK) for that block has not yet been reported for network element 110. Although missing data block 510 is represented as being detected after receipt of confirmation query 505 in figure 5, the relative order of these events it can be reversed as long as the confirmation query 505 is received by the mobile station 105 before it sends a PAN based on the event in response to the detection of the missing block 510.
5
10
15
20
25
30
Next, the mobile station 105 processes the confirmation query 505 (with such processing represented by the directed line marked 515) to prepare the appropriate DL consulted confirmation information to be returned to the network element 110 via a consulted confirmation response. 520. The queried confirmation response 520 is sent by the mobile station 105 to the network element 110 in the appropriate radio block period> N + 2 indicated in the confirmation query 505. As described above, the consulted confirmation response 520 can be , for example, a queried PAN 215 sent in response to confirmation query 505 corresponding with a query message by PAN, or a PDAN control message 230 sent in response to confirmation query 505 corresponding with a query message by PDAN 225. In the illustrated example, the DL confirmation queried information carried by the consulted confirmation response 520 includes the status of confirmation (for example, NACK) of the missing data block 510 because the element of formation of the receiving state 235 associated with the missing data block 510 is set to NO
REPORTED.
5
10
15
20
25
30
In addition, in preparation for sending an UL 525 RLC / MAC data block during the N + 2 radio block period, mobile station 105 performs event-based FANR and duplicate acknowledgment avoidance processing (with such processing represented by the directed line marked 530). Because the element of formation of the receiving state 235 associated with the missing data block 510 is set to NOT REPORTED, the event-based FANR procedure would typically proactively generate an event-based PAN (for example, automatically) for inclusion with the UL 525 RLC / MAC data block. However, using the techniques described here, the duplicate acknowledgment avoidance procedure implemented by mobile station 105 determines that the acknowledgment status (for example, NACK) of the missing data block 510 is also to be reported (or has a substantial probability of being reported) by the confirmed confirmation response 520. As such, mobile station 105 prevents your event-based FANR procedure from generating or at least sending an event-based PAN with the UL 525 RLC / MAC data, thereby improving bandwidth utilization and spectral efficiency (for example, saving 25 bits of data in a 3GPP EGPRS implementation see are 7).
Flowcharts representative of the exemplary processes that can be performed to implement any, some or all of the exemplary EGPRS 100 communication system, the exemplary mobile station 105, the exemplary RLC / MAC 115 transmitter, the exemplary RLC / MAC 120 receiver, the decoder 205 consultation form, the training of the
235 exemplary reception status, 240 exemplary acknowledged acknowledgment processor, 245 exemplary acknowledgment processor and 260 exemplary acknowledgment transmission unit are shown in figures 6A-B and 7.
5
10
15
20
25
30
In these examples, the process represented by each flowchart can be implemented by one or more programs comprising machine-readable instructions for execution by: (a) a processor, such as processor 812 shown in the exemplary processing system 800 discussed below in conjunction with the figure 8, (b) a controller and / or (c) any other suitable device. The one or more programs can be personified in software stored in a tangible medium such as, for example, a flash memory, a CD-ROM, a floppy disk, a hard drive, a DVD or a memory associated with the 812 processor, but all the program or programs and / or portions of it could be executed alternatively by a device other than the 812 processor and / or embodied in dedicated firmware or hardware (for example, implemented by an application specific integrated circuit (ASIC), a programmable logic device ( PLD), a field programmable logic device (FPLD), discrete logic, etc.). For example, any, some or all of the exemplary EGPRS 100 communication system, the exemplary mobile station 105, the exemplary RLC / MAC 115 transmitter, the exemplary RLC / MAC 120 receiver, the exemplary consultation decoder 205, the training of the 235 exemplary reception status, 240 exemplary acknowledged acknowledgment processor, 245 exemplary acknowledgment processor based on event could be
implemented by any combination of software, hardware and / or firmware. Also, some or all of the processes represented by the flowcharts of figures 6A-B and 7 can be implemented manually.
5
10
15
20
25
30
In addition, although the exemplary processes are described with reference to the flowcharts illustrated in figures 6A-B and 7, many other techniques for implementing the exemplary methods and apparatus described here can be used alternatively. For example, with reference to the flowcharts illustrated in figures 6A-B and 7, the execution order of the blocks can be changed and / or some of the described blocks can be changed, eliminated, combined and / or subdivided into multiple blocks.
An exemplary process 600 that can be performed to implement duplicate confirmation avoidance in the exemplary mobile unit 105 of figures 1 or 2, or both, is illustrated in figures 6A-B. Process 600 can be performed at predetermined intervals (for example, as before a next UL radio block period), based on an occurrence of a predetermined event (for example, such as detection of a data block from the Missing DL), as a background process, etc. or any combination of these. With reference to figures 1 and 2, the process 600 of figures 6A-B begins execution in block 605 of figure 6A in which the RLC / MAC receiver 120 at the mobile station 105 decodes any RLC / MAC data blocks of the DL 175 received from network element 110 during one or more radio block periods before a given radio block period in which mobile station 105 is for transmitting data. So, in block 610, the decoder
query 205 at mobile station 105 decodes any acknowledgment queries received from network element 110 during one or more radio block periods before a given radio block period in which mobile station 105 is to transmit data. For example, in block 610, query decoder 205 can decode a query message via PAN 210 or a query message via PDAN 225 requesting confirmation information from the queried DL from mobile station 105.
5
10
15
20
25
30
Then, control proceeds to block 615 in which the RLC / MAC transmitter 115 at mobile station 105 determines whether transmission processing for a given radio block period should begin. For example, in block 615, the RLC / MAC transmitter 115 can use any combination of query or interrupt-triggered processing to determine when to start transmission processing for the given radio block period. When transmission processing is to begin, control proceeds to block 620 in which the polled acknowledgment processor 240 at mobile station 105 determines whether any query messages requesting polled DL confirmation information to be sent during the given block period radio were decoded in block 610.
Control then proceeds to block 625 in which the acknowledgment processor based on event 245 at mobile station 105 identifies any RLC / MAC data blocks from the DL identified as missing during the decoding performed on block 605 and which have not yet been reported to the network element 110. For example, in block 625, the
event-based acknowledgment processor 245 implements the event-based FANR and processes the receiving state 235 formation used to track the status of the DL's RLC / MAC data blocks. As described above, a missing RLC / MAC data block from the DL is associated with an element in the formation of the receiving state 235 which is set to the UNREPORTED state when the data block is initially detected as missing and has not yet been reported for. the network element 110. Thus, in block 625, the acknowledgment processor based on event 245 determines whether the formation of the receiving state 235 has any elements set to the UNREPORTED state.
5
10
15
20
25
30
Then, control proceeds to block 630 in which the acknowledgment processor based on event 245 determines whether a PAN based on event 250 is to be transmitted during the given radio block period. For example, in block 630, the event-based acknowledgment processor 245 implements the event-based FANR and determines whether processing in block 625 identified any missing DL data blocks whose elements in forming reception state 235 are adjusted for the NOT REPORTED state. If no such missing, unreported DL data block has been identified in block 625, the acknowledgment processor based on event 245 determines that no PAN based on event 250 should be transmitted during the given radio block period (block 630) and the control proceeds to block 635 of figure 6B.
In block 635 of figure 6B, the queried confirmation processor 240 determines whether the processing in block 620 determined that the confirmation information
consulted from the DL was requested by a query of the network element 110 and must be sent during the given radio block period. If the DL confirmation query information is to be sent during the given radio block period (block 635), control proceeds to block 64 0 in which confirmation transmission unit 260 in confirmation transmission unit 260 determines that only the verified confirmation information must be sent and, therefore, no avoidance of duplicate confirmation is necessary. As such, the confirmation transmission unit 260 causes the DL's queried confirmation information to be sent using, for example, a consulted PAN 215 if the corresponding confirmation query decoded in block 610 was a query message by PAN 210 or a PDAN 230 control message if the corresponding confirmation query decoded in block 610 was a PDAN 225 consultation message or the mobile station has no uplink data to transmit. After the DL queryed confirmation information is sent in block 640, or if no DL queryed confirmation information is to be sent (block 635), the execution of the exemplary process 600 then ends.
5
10
15
20
25
30
Back to block 630 of figure 6A, if one or more missing data blocks of the DL NOT REPORTED have been identified in block 625, the event-based acknowledgment processor 245 determines that a PAN based on event 250 must be transmitted during the given radio block period (block 63 0) and control proceeds to block 645. At block 645, the query confirmation processor 240 determines whether processing at block 620
has determined that the confirmed confirmation information from the DL was requested by a query of the network element 110 and is also to be sent during the given radio block period. If the confirmation information consulted from the DL is not to be sent during the given radio block period (block 645), control proceeds to block 650 of figure 6B.
5
10
15
20
25
30
In block 650 of figure 6B, acknowledgment transmission unit 260 determines that only acknowledgment information based on the event must be sent and, therefore, no avoidance of duplicate acknowledgment is necessary. As such, acknowledgment transmission unit 260 causes confirmation information based on the DL event to be sent using, for example, a PAN field based on event 250. After processing in block 650 completes, execution of the 600 exemplary process ends.
Back to block 645 of figure 6A, if the DL confirmation query information is to be sent during the given radio block period, control proceeds to block 655 in which the confirmation transmission unit 260 implements a procedure of duplicate confirmation avoidance and assesses any associated confirmation omission criteria because duplicate confirmations queried and based on the event are scheduled to be sent in the given radio block period being processed. In the illustrated example, the confirmation transmission unit 260 is able to restrain the sending of the confirmation information based on the duplicated DL event as long as the consulted confirmation information from the DL is sent in the same block period.
radio regardless of whether the query-based and event-based confirmation information is scheduled to be sent at intervals other than the radio block period. In other words, although the queried confirmation information from the DL can be scheduled to be sent during a time period different from the given radio block period than the time period during which the consulted confirmation information from the DL is to be sent, control can proceed to block 655, as long as both confirmation information consulted and based on the event is scheduled to be sent in the same radio block period. In general, the duplicate confirmation avoidance procedure implemented in block 655 restrains the sending (for example, blocks) of a PAN based on the PAN 250 event carrying confirmation information based on the event if such confirmation information is also to be reported in a timely manner. by a consulted PAN 215 or a PDAN 230 control message carrying the consulted confirmation information. An exemplary procedure for implementing processing in block 655 is illustrated in figure 7 and described in more detail below.
5
10
15
20
25
30
After the block 655 duplicate acknowledgment avoidance procedure completes, control proceeds to block 660 where the acknowledgment transmission unit 260 determines whether the acknowledgment information based on the event scheduled to be transmitted is duplicated by the acknowledged acknowledgment information. to be reported and so can be omitted. Whether confirmation information based on the event scheduled to be transmitted can be omitted
(block 660), control proceeds to block 665 in which the confirmation transmission unit 260 causes only the confirmation information queried from the DL to be sent using, for example, the consulted PAN field 215 if the corresponding confirmation query decoded in block 610 it was a query message by PAN 210 or a control message PDAN 230 if the corresponding confirmation query decoded in block 610 was a query message by PDAN 225. After the confirmation information consulted from DL is sent in the block 665, the execution of the exemplary process 600 ends.
5
10
15
20
25
30
However, if the confirmation information based on the event scheduled to be transmitted cannot be omitted because it is not duplicated or there is a substantial probability that it will remain unreported if not sent (block 660), control proceeds to block 670 in which the acknowledgment transmission unit 2 60 causes the confirmation information based on the DL event to be sent using, for example, a PAN field based on the event 250. The control then proceeds to block 675 in which the transmission unit confirmation 260 causes the DL's queried confirmation information to be sent using, for example, the consulted PAN field 215 if the corresponding confirmation query decoded in block 610 was a query message by PAN 210 or a PDAN control message 230 if the corresponding confirmation query decoded in block 610 was a query message via PDAN 225. After the DL confirmation information is sent in blocks 670 and 675, the execution of the exemplary process 600 ends.
5
10
15
20
25
30
An exemplary procedure 655 for implementing duplicate confirmation avoidance processing and evaluation of the associated confirmation omission criteria in block 655 of figure 6A is illustrated in figure 7. With reference to figures 1 and 2, the exemplary procedure 655 of figure 7 begins under a condition that the event-based PAN 250 carrying confirmation information based on the DL event is scheduled to be transmitted during a given radio block period being processed, and any of the queried PAN 215 or the PDAN 230 control message carrying the confirmed confirmation information from the DL is also scheduled to be transmitted during the given period. With that in mind, procedure 655 of figure 7 begins execution at block 705 in which the confirmation transmission unit 260 at the mobile station 105 determines whether the evaluation of any confirmation omission criteria is enabled. If the evaluation of the confirmation omission criteria is not enabled (block 705), control proceeds to block 710 in which the confirmation transmission unit 260 pre-defines to indicate that the confirmation information based on the DL event to be carried by the PAN based on event 250 can be omitted because it is a duplicate of the queried confirmation information from the DL to be carried by any of the consulted PAN 215 or the PDAN 23 0 control message, and all the consulted confirmation information from the DL is substantially likely to be received by the network element 110. The execution of the exemplary procedure 655 then ends.
However, if the evaluation of the criteria for omission of
confirmation is enabled (block 705), control proceeds to block 715 in which the confirmation transmission unit 260 evaluates a channel quality criterion indicating whether an estimated UL channel quality satisfies a threshold. If the estimated quality of the UL channel does not satisfy (for example, not greater than or equal to) the specified threshold (block 715), control proceeds to block 720 in which the acknowledgment transmission unit 260 evaluates a criterion of the type of consulted response indicating whether the consulted DL confirmation information is to be transmitted via a consulted PAN 215 or a PDAN 23 control message 0. If the consulted DL confirmation information is to be transmitted via consulted PAN 215 (block 720), control proceeds to block 725 in which acknowledgment transmission unit 260 indicates that acknowledgment information based on the DL event to be carried by the PAN based on event 250 cannot be omitted because there is a substantial probability that it is not received by the network element 110 if the PAN based on event 250 is not sent and only the confirmed confirmation information from the DL is sent by any one of the PAN consul 215 or the PDAN 230 control message. The execution of the exemplary procedure 655 then ends.
5
10
15
20
25
30
If, however, the confirmation information consulted from the DL is to be transmitted via the PDAN 230 control message (block 720), or if the estimated quality of the UL channel satisfies (for example, it is greater than or equal to) the specified threshold (block 715), control proceeds to block 730 in which the transmission unit
acknowledgment 260 evaluates a criterion of the amount of confirmation remaining indicating whether the amount of confirmation information remaining to be sent exceeds a threshold. If the remaining confirmation information to be sent (characterized, for example, by the difference between the highest BSN of all blocks successfully received and the lowest BSN of all blocks not yet successfully received) exceeds the specified threshold (block 730), control continues to block 725, the operation of which is described above. However, if the remaining confirmation information to be sent does not exceed the specified threshold (block 730), control proceeds to block 735.
5
10
15
20
25
30
In block 735, acknowledgment transmission unit 260 evaluates a downlink channel assignment criterion indicating whether the downlink channel assignment exceeds a threshold data rate or bandwidth. If the downlink channel assignment exceeds the specified threshold (block 735), control proceeds to block 725, the operation of which is described above. However, if the downlink channel assignment does not exceed the specified threshold (block 735), control proceeds to block 740.
In block 740, confirmation transmission unit 260 evaluates a query response scheduling criterion indicating whether DL consulted confirmation information is scheduled to be transmitted in the given radio block period during which event-based confirmation information DL is scheduled to be broadcast or a subsequent radio block period. The scheduling criterion of the consulted response has
applicability primarily to systems where the acknowledgment transmission unit 260 can also restrain the sending of confirmation information based on the DL event if a queried response sending duplicate acknowledgment information is scheduled to be sent during a radio block period after the given radio block period. If the confirmation information consulted from the DL is scheduled to be transmitted during a later radio block period (block 740), control proceeds to block 725, the operation of which is described above. However, if the DL confirmation query information is scheduled to be transmitted during the same radio block period as the DL event based confirmation information (block 740), control proceeds to block 710, the operation of which is described above.
5
10
15
20
25
30
As shown in figure 7, in an exemplary implementation, any, some or all of the criteria represented by blocks 715, 720, 730, 735 and 740 can be evaluated to determine whether confirmation information based on the DL event to be carried by PAN based on event 25 0 can be omitted because it is duplicative and has a substantial probability of being reported by the DL queryed confirmation information to be carried by any of the queried PAN 215 or the PDAN 230 control message.
As yet another example, the duplicate confirmation avoidance techniques described here can be implemented in a communication system in accordance with the 3GPP EGPRS version system by appropriately modifying the technical specification (TS) 3GPP 44.060, V7.17.0 (May
5
10
15
20
25
30
2009), which is incorporated herein by reference in its entirety. An exemplary modification in 3GPP TS 44.060 to support the duplicate confirmation avoidance techniques described here is to replace the existing second paragraph in section 9.1.14.3 with the following text:
"If the final RLC receiver is the mobile station, the event-based FANR is enabled for this temporary block flow (TBF) and the mobile station has at least one TBF assigned in the direction of the uplink, the mobile station must insert a PAN field in an EGPRS RLC / MAC block for transferring data transmitted during a given radio block period to that uplink TBF if the state of any element in the formation of the receiving state V (N) is NOT REPORTED and otherwise it would remain UNREPORTED if no PAN based on the event was transmitted, considering any ACK / NACK information transmitted during the radio block period in response to a query (both for a PAN, for an ACK / NACK message from the DOWNWORD LINK) OF EGPRS PACKAGE as for an EGPRS PACKAGE LINK ACK / NACK TYPE 2 message. The mobile station can continue to insert PAN fields into subsequent EGPRS RLC / MAC data blocks sent on the same radio block period as long as there is one or more elements in the formation of the receiving state V (N), whose state is NOT REPORTED. "
Figure 8 is a block diagram of an exemplary 800 processing system capable of implementing the apparatus and methods disclosed here. The processing system 800 can correspond with, for example, a platform of
mobile station processing, a network element processing platform, a server, a personal computer, a personal digital assistant (PDA), an Internet device, a mobile phone or any other type of computing device.
5
10
15
20
25
30
The 800 system in the current example includes an 812 processor, such as a general-purpose programmable processor, an embedded processor, a microcontroller, etc. The processor 812 includes a local memory 814 and executes coded instructions 816 present in the local memory 814 and / or in another memory device. The 812 processor can execute, among other things, machine-readable instructions to implement the processes represented in figures 6A-B or 7, or both. The 812 processor can be any type of processing unit, such as one or more microprocessors from the Intel® Centrino® processor family, from the Intel® Pentium® processor family, from the Intel® Itanium® processor family and / or from the Intel® XScale® processors, one or more microcontrollers from the ARM® microcontroller family, from the PIC® microcontroller family, etc. Of course, other processors from other families are also appropriate.
The processor 812 communicates with a main memory including a volatile memory 818 and a non-volatile memory 820 via a bus 822. The volatile memory 818 can be implemented by static random access memory (SRAM), synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), dynamic random access memory
RAMBUS (RDRAM) and / or any other type of
random access memory. Non-volatile memory 820 can be implemented by flash memory and / or any other desired type of memory device. Access to main memory 818, 820 is typically controlled by a memory controller (not shown).
5
10
15
20
25
30
Computer 800 also includes an interface circuit 824. The interface circuit 824 can be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB) and / or an input / output interface third generation (3GIO).
One or more 826 input devices are connected to the 824 interface circuit. 0 826 input device (s) allows a user to enter data and commands into the 812 processor. 0 input can be implemented by, for example, a keyboard, a mouse, a touch screen, a touch pad, a touch sensitive sphere, an isoponto and / or a voice recognition system.
One or more output devices 828 are also connected to interface circuit 824. Output devices 828 can be implemented, for example, by display devices (for example, a liquid crystal display, a cathode ray tube monitor ( CRT)), a printer and / or speakers. The 824 interface circuit thus typically includes a graphics driver.
The 824 interface circuit also includes a communication device, such as a modem or network interface card, to facilitate the exchange of data with
external computers over a network (for example, an Ethernet connection, a digital subscriber line (DSL), a telephone line, coaxial cable, a cellular telephone system such as an EGPRS compliant system, etc.).
Computer 800 also includes one or more mass storage devices 830 for storing software and data. Examples of such mass storage devices 830 include floppy disk drives, hard disk drives, compact disk drives and digital versatile disk drives (DVD). The mass storage device 830 can store the formation of the reception state V (N) 235. Alternatively, the volatile memory 818 can store the formation of the reception state V (N) 235.
As an alternative to implementing the methods and / or devices described here in a system, such as the device in figure 8, the methods and or devices described here can be embedded in a structure, such as a processor and / or an ASIC (integrated circuit) specific application).
5
10
15
20
25
Finally, although certain exemplary methods, devices and articles of manufacture have been described here, the scope of coverage of that patent is not limited to them. On the contrary, this patent covers all methods, devices and articles of manufacture that fall regularly within the scope of the appended claims, both literally and under the doctrine of equivalents.
5
10
15
20
25
30

权利要求:
Claims (15)
[0001]
1. Method for a mobile station capable of sending event-based confirmation information, the method characterized by comprising: classifying a first downlink data block as unreported; determine whether or not a query is received from a network by asking the mobile station to send confirmation information over a period; determine whether or not to send event-based confirmation information for the first downlink data block classified as unreported based on whether or not the mobile station should also send query information queried to the first during the period downlink data block classified as unreported; send event-based acknowledgment information for the first downlink data block classified as unreported during the period if the base station should not send any queried confirmation information for the first downlink data block classified as unreported during the period not reported; and curb sending during the period the event-based confirmation information for the first downlink data block classified as unreported if the base station is to send the queried confirmation information for the first downlink data block during the period classified as unreported.
[0002]
2. Method according to claim 1, characterized by the fact that the event-based confirmation information comprises a superimposed ACK / NACK (PAN) field according to a fast ACK / NACK (FANR) reporting procedure with based on enhanced general packet radio service (EGPRS) event or an ACK / NACK field in an EGPRS ACK / NACK control message. 5 10 15 20 25 30
[0003]
3. Method, according to claim 2, characterized by the fact that the acknowledged confirmation information comprises at least one of a PAN field or an ACK / NACK field in an EGPRS ACK / NACK control message.
[0004]
4. Method according to claim 1, characterized by the fact that classifying the first downlink data block as unreported comprises adjusting an element of a formation from the receiving state to an unreported state, the element corresponding to the first downlink data block.
[0005]
5. Method, according to claim 1, characterized by the fact that the period is a radio block period.
[0006]
6. Tangible storage device characterized by storing machine-readable instructions that, when executed, cause a machine capable of sending event-based confirmation information: classify a first downlink data block as unreported, determine whether or not it should a query is received from a network asking the machine to send the confirmation information consulted for a period, determine whether or not to send event-based confirmation information during the period for the first downlink data block classified as not reported based on whether or not the machine should also send query information queried during the first downlink data block classified as unreported during the period; 5 10 15 20 25 30 send during the period the event-based confirmation information for the first downlink data block classified as unreported if the machine should not send any queried confirmation information for the first data block during the period downlink link classified as unreported; and curb sending during the period of the event-based confirmation information for the first downlink data block classified as unreported if the machine should send during the period the queried confirmation information for the first classified downlink data block as not reported.
[0007]
7. Storage device according to claim 6, characterized by the fact that, in order to classify the first downlink data block as unreported, the instructions, when executed, additionally cause the machine to adjust an element of a formation of the receiving state to an unreported state, the element corresponding to the first data block of the downlink.
[0008]
8. Storage device according to claim 6, characterized by the fact that the period is a radio block period.
[0009]
9. Storage device according to claim 6, characterized by the fact that the event-based confirmation information comprises a superimposed ACK / NACK (PAN) field according to a rapid ACK / NACK (FANR) reporting procedure based on event of the enhanced general packet radio service (EGPRS) or an ACK / NACK field in an EGPRS ACK / NACK control message. 5 10 15 20 25 30
[0010]
10. Storage device according to claim 6, characterized by the fact that the confirmation information consulted comprises at least one of a PAN field or an ACK / NACK field in an ACPR / NACK control message from EGPRS.
[0011]
11. Mobile station capable of sending event-based confirmation information, the mobile station characterized by comprising: a processor, the processor being configured to: classify a first downlink data block as unreported, determine whether or not a query is received from a network requesting that the mobile station send the confirmation information consulted for a period; determine whether or not to send event-based confirmation information during the first downlink data block classified as unreported based on whether or not the mobile station should also send query information queried to the first during the period downlink data block classified as unreported; send event-based confirmation information for the first link data block 5 10 15 20 25 30 descending classified as unreported during the period, if the mobile station should not send any query confirmation information for the first link during the period downlink data block classified as unreported, and curb sending during the event-based confirmation information period for the first downlink data block classified as unreported if the mobile station should send the information during the period confirmation query for the first downlink data block classified as unreported.
[0012]
12. Mobile station according to claim 11, characterized by the fact that the event-based confirmation information comprises a superimposed ACK / NACK (PAN) field according to a rapid ACK / NACK (FANR) reporting procedure in the event of the general improved radio service (EGPRS) or an ACK / NACK field in an EGPRS ACK / NACK control message.
[0013]
13. Mobile station, according to claim 11, characterized by the fact that the confirmation information consulted comprises at least one of a PAN field or an ACK / NACK field in an EGPRS ACK / NACK control message.
[0014]
14. Mobile station according to claim 11, characterized by the fact that to classify the first downlink data block as unreported, the processor must set an element of a receiving state formation to an unreported state, the element corresponding to the first downlink data block.
[0015]
15. Mobile station, according to claim 11, characterized by the fact that the period is a radio block period.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112012008171B1|2021-03-30|METHOD FOR A MOBILE STATION ABLE TO SEND CONFIRMATION INFORMATION BASED ON EVENT, TANGIBLE STORAGE DEVICE AND MOBILE STATION

---

US8204003B2|2012-06-19|Mobile station transmissions in response to network acknowledgment polling

---

EP3075093B1|2018-10-10|Methods, apparatuses and user equipment for hybrid automatic repeat request transmission

---

BR112019019785A2|2020-04-22|method and device for sending return information, receiving return information and computer storage medium

---

US8644294B2|2014-02-04|Methods and apparatus to use window alignment information to process acknowledgment information associated with transmitted data blocks

---

WO2017121275A1|2017-07-20|Scheduling method, scheduler and network access device

---

BRPI0721372B1|2019-09-03|method for use in a cellular access system, radio base station and user equipment

---

CN101359980A|2009-02-04|Exception processing method in RLC data transmission process

---

CN114070498A|2022-02-18|Method and device for determining downlink allocation indication, method and device for configuring downlink allocation indication, storage medium, terminal, and base station

同族专利:

---

公开号 | 公开日

---

CN102598761A|2012-07-18|

---

EP2290862A3|2013-11-20|

---

KR101362628B1|2014-02-12|

---

WO2011022822A1|2011-03-03|

---

HK1252901A1|2019-06-06|

---

BR112012008171A2|2016-03-01|

---

KR20130135968A|2013-12-11|

---

US20130258952A1|2013-10-03|

---

US9282543B2|2016-03-08|

---

AU2010286289A1|2012-03-08|

---

KR101362609B1|2014-02-12|

---

US8457048B2|2013-06-04|

---

EP3297198A1|2018-03-21|

---

EP2290862A2|2011-03-02|

---

CA2772667A1|2011-03-03|

---

JP5420769B2|2014-02-19|

---

CA2772667C|2016-04-19|

---

KR20120050491A|2012-05-18|

---

ES2665435T3|2018-04-25|

---

SG178417A1|2012-04-27|

---

JP2013503505A|2013-01-31|

---

EP2290862B1|2018-01-10|

---

CN102598761B|2015-07-29|

---

AU2010286289B2|2014-08-14|

---

US20110051661A1|2011-03-03|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US6643813B1|1999-02-17|2003-11-04|Telefonaktiebolaget Lm Ericsson |Method and apparatus for reliable and efficient data communications|

---

US6882637B1|1999-10-14|2005-04-19|Nokia Networks Oy|Method and system for transmitting and receiving packets|

---

JP4295051B2|2003-09-12|2009-07-15|パナソニック株式会社|Transmitting apparatus and transmitting method|

---

US8761202B2|2004-09-27|2014-06-24|Raghupathy Sivakumar|Architecture for dynamically adaptive transport protocols|

---

WO2007063393A2|2005-11-30|2007-06-07|Nokia Corporation|Apparatus, method and computer program product providing retransmission utilizing multiple arq mechanisms|

---

CN101043299B|2006-04-05|2010-08-25|华为技术有限公司|ACK/NACK method|

---

EP2008391B1|2006-04-19|2014-01-15|Telefonaktiebolaget LM Ericsson |Method and apparatus for improved data communication in cellular access systems|

---

DE602006008584D1|2006-05-08|2009-10-01|Panasonic Corp|Transmission of data packets in a wireless communication network|

---

WO2007136038A1|2006-05-19|2007-11-29|Panasonic Corporation|Logic address allocation method|

---

JP4811165B2|2006-07-24|2011-11-09|株式会社ケンウッド|Polling communication system, host device, terminal device, polling communication method and program|

---

CN101517952A|2006-08-30|2009-08-26|诺基亚公司|Method and apparatus for fast or negative acknowledgement in a mobile communication system|

---

EP2119085B1|2007-01-24|2010-10-20|ViaSat, Inc.|Enhanced error control communication systems and methods|

---

GB0701668D0|2007-01-29|2007-03-07|Tang Bob|Immediate ready implementation of virtually congestion free guaranteed service capable network: external internet nextgenTCP nextgenFTP nextgenUDPs|

---

CN101689973B|2007-05-08|2013-05-22|交互数字技术公司|Method and apparatus for providing piggybacked positive acknowledgement/negative acknowledgement field indicator and a polling indicator|

---

KR101461970B1|2007-09-13|2014-11-14|엘지전자 주식회사|Method of performing polling procedure in a wireless communication system|

---

DK2215763T3|2007-11-02|2012-10-22|Ericsson Telefon Ab L M|Methods and apparatus for processing error checking messages in a wireless communication system|

---

US20100105334A1|2008-04-25|2010-04-29|Interdigital Patent Holdings, Inc.|Radio link control status reporting and polling|

---

US8321741B2|2008-05-05|2012-11-27|Industrial Technology Research Institute|System and apparatus for providing an adaptive control mechanism for wireless communications|

---

US8295159B2|2009-01-14|2012-10-23|Qualcomm Incorporated|Timer poll retransmission expiry in a wireless communication system|

---

EP2443769B1|2009-06-18|2018-03-28|LG Electronics Inc.|Method for transmitting packet downlink ack/nack information in a wireless communication system and apparatus for the same|

---

US8457048B2|2009-08-31|2013-06-04|Research In Motion Limited|Methods and apparatus to avoid mobile station transmission of duplicate event-based and polled acknowledgments|EP2008391B1|2006-04-19|2014-01-15|Telefonaktiebolaget LM Ericsson |Method and apparatus for improved data communication in cellular access systems|

---

US9762358B2|2009-02-18|2017-09-12|Idtp Holdings, Inc.|Data retransmission scheme|

---

US8457048B2|2009-08-31|2013-06-04|Research In Motion Limited|Methods and apparatus to avoid mobile station transmission of duplicate event-based and polled acknowledgments|

---

US20110069669A1|2009-09-11|2011-03-24|Research In Motion Limited|System and methods for sending and receiving panso as to avoid decoding confusion|

---

US8898078B2|2010-05-21|2014-11-25|Microsoft Corporation|Scalable billing with de-duplication in aggregator|

---

US8380736B2|2010-05-21|2013-02-19|Microsoft Corporation|De-duplication in billing system|

---

US8837388B2|2010-07-22|2014-09-16|Blackberry Limited|Methods and apparatus to perform assignments in wireless communications|

---

US8745231B2|2010-07-22|2014-06-03|Blackberry Limited|Methods and apparatus to poll in wireless communications|

---

US8830981B2|2010-07-22|2014-09-09|Blackberry Limited|Methods and apparatus to poll in wireless communications based on assignments|

---

US9001649B2|2010-07-22|2015-04-07|Blackberry Limited|Methods and apparatus to communicate data between a wireless network and a mobile station|

---

US20120079336A1|2010-09-24|2012-03-29|Aran Bergman|Techniques utilizing arq feedback for efficient transmitter buffer usage|

---

US8755403B2|2011-11-09|2014-06-17|Hitachi, Ltd.|Block acknowledgement for wireless communication methods, apparatuses and systems|

---

US9391755B2|2013-05-13|2016-07-12|Telefonaktiebolaget Lm Ericsson |Radio access network node and mobile station with increased Ack/Nack space for packet downlink Ack/Nack message|

---

CN105429728A|2014-09-17|2016-03-23|中兴通讯股份有限公司|Pending block sending method and device|

---

US9614567B2|2015-03-19|2017-04-04|Qualcomm Incorporated|Systems and methods for recovering from stalls on a mobile device|

---

CN106921619B|2015-12-24|2020-04-14|阿里巴巴集团控股有限公司|Associated event processing method and device|

---

JPWO2020054022A1|2018-09-13|2021-09-16|オリンパス株式会社|Communication systems, receiving terminals, communication methods, and programs|

法律状态:
2018-05-29| B25D| Requested change of name of applicant approved|Owner name: BLACKBERRY LIMITED (CA) |

---

2019-01-08| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|

---

2019-12-24| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|

---

2020-01-21| B15K| Others concerning applications: alteration of classification|Free format text: A CLASSIFICACAO ANTERIOR ERA: H04W 28/04 Ipc: H04L 1/16 (2006.01), H04L 1/18 (2006.01) |

---

2021-03-09| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|

---

2021-03-30| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 10 (DEZ) ANOS CONTADOS A PARTIR DE 30/03/2021, OBSERVADAS AS CONDICOES LEGAIS. |

优先权:

---

申请号 | 申请日 | 专利标题

---

US12/551,161|2009-08-31|

---

US12/551,161|US8457048B2|2009-08-31|2009-08-31|Methods and apparatus to avoid mobile station transmission of duplicate event-based and polled acknowledgments|

---

PCT/CA2010/001308|WO2011022822A1|2009-08-31|2010-08-31|Methods and apparatus to avoid mobile station transmission of duplicate event-based and polled acknowledgments|

---